The created documentation from the pull request is available at: docu-html

Hi @jorgecasal, this change looks great – Thanks!
I am keen to import your change into our internal repository via copybara and export it back to baselibs.
In order to do so, I would like to ask you to squash your commits together (or rebase them in a suitable way, the merge-commit is likely to cause trouble otherwise).

Hi @fbaeuerle, thanks for the feedback!
I've squashed the commits into a single one. Let me know if you need anything else.

Hi @jorgecasal,
currently, no further action from your side is needed. I also adapted communication (and the other users) because the code is stored in the same repository internally. I have to get this through code review and afterwards I will export it back to baselibs using copybara. It will, however, take some more additional time.

Hi @jorgecasal,
We successfully integrated your change and exported it back to baselibs via copybara:
1198d85

I also adapted communication to your change, my coworker will export that change soon.

Hi @fbaeuerle,
Can you confirm that issue eclipse-score/communication#94 will be resolved by your coworker's changes, and no further action is needed from my side?
Thanks!

Yes, basically the code in communication will adhere to the changed class interface that you contributed to baselibs. The
code lives in the same repo internally, so I had to adapt this in order to integrate it.

Whereas I am one of the persons responsible for importing from/exporting to baselibs, there's a bunch of coworkers responsible for this task in the communication repository.

I will double check this after it was exported. It can happen that some part of communication exempt from the sync to the internal repository needs adaptation, but @Rahul-Sutariya will find that out when exporting the change.